The include path does not match the converted submodule location. This PR adds app/Domain/Connector/Templates/submodules/importProgress.blade.php, so connector::partials.importProgress will likely fail view resolution at runtime. Update the include to the expected convention (e.g., connector::submodules.importProgress) or move/alias the Blade file so that connector::partials.importProgress exists.

This JavaScript is syntactically invalid (ready(function() { ... } ); has mismatched braces/parentheses). It will prevent initProjectTable() from running and may break subsequent scripts. Fix the $(document).ready(...) closure to a valid structure (or convert to jQuery(function(){ ... });).

This template is an empty Blade view. If it is referenced by a route/controller, it will render a blank page and effectively regress the UI. Either remove the file if it’s not meant to exist, or replace it with the converted template content (likely @extends($layout) + a @section('content') implementation or an @include(...) delegate).

This template is an empty Blade view. If it is referenced by a route/controller, it will render a blank page. Either remove it if unused or populate it with the correct Blade implementation / delegate include.

The class attribute value \"color: {{ ... }}\" is not a valid CSS class name pattern (it looks like an attempted inline style). This will not apply coloring as intended. Use a real CSS class (e.g., class=\"{{ $row['colorClass'] }}\") or move the value into style (e.g., style=\"color: ...\") depending on how colorClass is meant to be used.

This builds a POST action URL directly from $_GET values. Even though {{ }} HTML-escapes, it does not URL-encode query params, and it couples the view to raw superglobals. Prefer using request/query helpers and proper query building (e.g., using request()->query() / http_build_query / a route helper with ->withQueryString()), so special characters don’t break the URL and the view stays framework-consistent.

The legacy template rendered description unescaped, while this Blade version escapes HTML. If provider descriptions contain intended markup (links/icons), this will now render as literal text and change the UI. Decide on the contract: if descriptions are trusted HTML, render with {!! ... !!} (ideally sanitized upstream); if they are meant to be plain text, ensure providers don’t supply HTML and consider updating the old behavior accordingly.

This is a POST form without a CSRF token. Some converted templates now use @csrf (e.g., API key deletion), so this should be made consistent to avoid CSRF vulnerabilities and potential 419/CSRF validation failures depending on middleware configuration. Add @csrf inside the form.

The $ticket assignment is not used anywhere in this template. Since this file is short and self-contained, removing the dead assignment will reduce noise and make the template easier to maintain.

This partial emits an inline <script> directly. Since similar templates in this PR are moving scripts into @once @push('scripts'), consider doing the same here. It keeps script placement consistent with the layout (often collected near the end of the page), reduces the chance of duplicate execution if the partial is included more than once, and makes script management easier.

The integration navigation links point to /submodules.importProgress/integration..., which does not match the legacy route (/connector/integration...) and is very likely a broken URL. Update both the "Go Back" and "Confirm" hrefs to use the connector integration route.

Several URLs within this template use the /submodules.importProgress/integration path, which appears to be an unintended substitution and will likely break navigation. Use the expected connector route (/connector/integration) for the form action and Back link; also the translation key headlines.submodules.importProgress looks incorrect for a page title and should be changed to the appropriate existing headline key used for connector pages.

Several URLs within this template use the /submodules.importProgress/integration path, which appears to be an unintended substitution and will likely break navigation. Use the expected connector route (/connector/integration) for the form action and Back link; also the translation key headlines.submodules.importProgress looks incorrect for a page title and should be changed to the appropriate existing headline key used for connector pages.

Several URLs within this template use the /submodules.importProgress/integration path, which appears to be an unintended substitution and will likely break navigation. Use the expected connector route (/connector/integration) for the form action and Back link; also the translation key headlines.submodules.importProgress looks incorrect for a page title and should be changed to the appropriate existing headline key used for connector pages.

Several URLs within this template use the /submodules.importProgress/integration path, which appears to be an unintended substitution and will likely break navigation. Use the expected connector route (/connector/integration) for the form action and Back link; also the translation key headlines.submodules.importProgress looks incorrect for a page title and should be changed to the appropriate existing headline key used for connector pages.

The "Go back to integrations" link points to /submodules.importProgress/show, which likely does not exist; the legacy template linked to /connector/show. Update the href to the connector show route so users can navigate back successfully.

The first project-name <td> is never closed before starting the next <td>, resulting in invalid table markup. Add a closing </td> after the project link to keep the table structure valid and avoid layout/JS table plugin issues.

This template reads $_GET['id'] directly in the view. Prefer passing $id from the controller (or using request()->route('id') / request()->query('id')) so the view is not coupled to PHP superglobals and routing/query shape. This also makes the template easier to test and reuse.

This POST form is missing @csrf. Since addEvent.blade.php was updated to include @csrf, the edit/delete calendar forms should be consistent to avoid CSRF vulnerabilities and potential 419 errors under Laravel's CSRF middleware.

The Back link has an unterminated href attribute (missing closing quote/brace), which will break the rendered HTML and can make subsequent markup invalid. Fix the href to properly close the Blade expression.

This page uses a likely incorrect translation key (headlines.submodules.importProgress) and routes all wizard actions to /submodules.importProgress/integration/..., which looks unintended (and inconsistent with /connector/... elsewhere). Update the headline key and correct the form/back URLs to the Connector integration endpoint.

This page uses a likely incorrect translation key (headlines.submodules.importProgress) and routes all wizard actions to /submodules.importProgress/integration/..., which looks unintended (and inconsistent with /connector/... elsewhere). Update the headline key and correct the form/back URLs to the Connector integration endpoint.

This page uses a likely incorrect translation key (headlines.submodules.importProgress) and routes all wizard actions to /submodules.importProgress/integration/..., which looks unintended (and inconsistent with /connector/... elsewhere). Update the headline key and correct the form/back URLs to the Connector integration endpoint.

The success page uses what appears to be an invalid translation key and links back to {{ BASE_URL }}/submodules.importProgress/show, which likely should be the Connector integrations listing (e.g., /connector/show). As written, users may land on a 404 after completing an integration.

This is a POST form but it does not include a CSRF token. Add @csrf inside the form to prevent CSRF vulnerabilities.

This delete action submits via POST but does not include a CSRF token. Add @csrf so board deletion cannot be triggered cross-site.

Blade {{ ... }} already escapes output; wrapping with e() can lead to double-escaping (e.g., & showing as &). Use a single escaping mechanism (typically just {{ $canvasTitle }} here).

This directly indexes into $canvasTypes[$canvasItem['box']] without fallback, but the template itself sets defaults where box can be an empty string. That combination can trigger an undefined index/offset error. Use a safe default (null coalescing) for icon/title or ensure canvasItem['box'] is always valid before rendering this line.

In the legacy template the provider description was output unescaped (allowing markup). Here it is escaped, which can break formatting if descriptions contain HTML; elsewhere (show.blade.php) the description is still rendered unescaped. Use a consistent approach across Connector templates (either sanitize and escape everywhere, or intentionally render trusted HTML with {!! ... !!}).